<!doctype html>
<meta charset=utf-8>
<title>Disposition of comments for Media Queries CR</title>
<style>
body { font-family: sans-serif; margin: 1em }

table { 
  border-collapse: collapse; margin: 1em 0; empty-cells: show;
}

th, td { 
  text-align: left;
  vertical-align: top;
  border: thin solid black;
  padding: 0.2em;
}

pre {
  font-size: 0.8em;
}

.proposal { background: orange }
.rejected { background:red }

.source {
  background: silver;
  font-size: 1.2em;
  padding: 0.3em;
}

.source a { text-decoration: none }

.a { background:lightgreen }
.r { background:orange }
.fo { background:red }

</style>

<h1>Disposition of comments for Media Queries CR</h1>

<p>This document is a proposed disposition of comments between the <a href="http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/">Media Queries 6 June 2007 CR</a> and the <a href="http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090423/">Media Queries 23 April 2009 CR</a>.</p>

<p>The following color coding convention is used for comments:</p>

<ul>
 <li class=a>The CSS WG agreed with the reviewer.
 <li class=r>The CSS WG disagreed with the reviewer.
 <li class=fo>The CSS WG disagreed with the reviewer and the reviewer raised a Formal Objection.
</ul>

<p>(There were no formal objections.)</p>

<table>



<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0077.html">Comment</a> from fantasai Mon, 13 Aug 2007.
<tr class=r><td>1<td>
<p>The poster suggested that it would be more useful to use the media *groups*
defined in CSS2.1 [1]. E.g.
<pre>
   @media paged { ... }
</pre>
<td>Too late for this version. We should reconsider this for Media Queries Level 4.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0101.html">Comment</a> from fantasai  Tue, 21 Aug 2007.
<tr class=r><td>2<td>
Today we discussed how imprecision in device hardware results in
display widths and heights that are not *exactly* in line with the
nominal width and height. It was suggested that we should allow
some fuzz factor in media query matching for this reason.

<td>No change.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0097.html">Comment</a> from fantasai Tue, 21 Aug 2007.
<tr class=a><td>3<td>
<pre>
Proposed changes:

   http://www.w3.org/TR/css3-mediaqueries/#device-aspect-ratio

   # In this specification, aspect ratio is defined as the number of
   # horizontal pixels over the number of vertical pixels.

   change to

   | In this specification, aspect ratio is defined as the horizontal
   | length of the device's display divided by its vertical length.


   http://www.w3.org/TR/css3-mediaqueries/#resolution

   # The 'resolution' media feature describes the resolution of the
   # output device, i.e. the density of the pixels.

   Add

   | When querying devices with non-square pixels, in 'min-resolution'
   | queries the least-dense dimension must be compared to the specified
   | value and in 'max-resolution' queries the most-dense dimensions must
   | be compared instead. A fixed 'resolution' query never matches a device
   | with non-square pixels.

   (Alternatively we could allow two values to query each dimension
   independently, but I don't think this is useful.)
</pre>
<td>Accepted.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0119.html">Comment</a> from Stewart Brodie Wed, 22 Aug 2007.
<tr class=a><td>4<td>

<pre>
'not' and unknown media types:

Section 3 says: "The presence of the keyword 'not' at the beginning of the
query negates the results."  Section 4 says: "Media queries involving
unknown media types are always false".

When I read that, the word 'always' led me to wonder whether or not unknown
media types trump the section 3 definition of 'not'.  I suggest the
following clarifications:

1) remove the word "always" from the section 4 statement
2) Add an example showing that the following media query is true:

     @media not 3d-glasses { ... }
</pre>

<td>
'not foo' is true and 'foo' is false. (3d-glasses is a parse error.)

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0120.html">Comment</a> from Stewart Brodie Wed, 22 Aug 2007. 

<tr class=a><td>5<td>
Does "color-index" have a zero value unless a lookup table is used?
<td>
If the device does not use a color lookup table, the value is zero.


<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Aug/0201.html">Comment</a> from Andrew Fedoniouk Tue, 28 Aug 2007.
<tr class=r><td>6<td>
<p>Is it possible to add in media queries [1] value that will 
indicate that UA is running with high-contrast-screen settings?
<td>Too late for this version. We should reconsider this for Media Queries Level 4.





<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0065.html">Comment</a> from Ian Hickson 6 Nov 2007
<tr class=a><td>7<td>
<p>it'd be nice if we defined the lack of a media query string to mean "all"

<td>Yes.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0125.html">Comment</a> from Henri Sivonen 14 Nov 2007.
<tr class=a><td>8<td>
<p>Parsing is not well defined in terms of whitespace and error handling.

<td>This is now addressed by the syntax section.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0209.html">Comment</a> from Henri Sivonen 17 Nov 2007.

<tr class=r><td>9<td>
<p>If a media feature does not match the media type is that an error?

<td>No. Writing "speech and (width:100px)" is acceptable. The validator may issue a warning though.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Nov/0212.html">Comment</a> from Henri Sivonen 17 Nov 2007.
<tr class=a><td>10<td>
<p>grid doesn't apply to all media

<td>Fixed, thanks!

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0005.html">Comment</a> from Anne van Kesteren 03 Dec 2007.
<tr class=r><td>11<td>

<p>I think that the Media Queries draft  
http://www.w3.org/TR/2007/CR-css3-mediaqueries-20070606/ should either  
define media types itself or should reference CSS 2.1 for them.  
Referencing HTML4 and CSS2 for these seems outdated. For instance, "aural"  
is deprecated in CSS 2.1, but "speech" is not. "speech" is not mentioned  
in Media Queries and "aural" is used in examples and mentioned several  
times.

<td>Too late for this version. We should reconsider this for Media Queries Level 4.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0038.html">Comment</a> from Anne van Kesteren 10 Dec 2007.
<tr class=a><td>12<td>Syntax issues.

<td>Addressed. (Syntax is now described in terms of CSS 2.1 eliminating these issues.)

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0051.html">Comment</a> from Anne van Kesteren 12 Dec 2007.
<tr class=a><td>13<td>Using the same syntax rules for HTML and CSS.

<td>Addressed by using <a href="http://lists.w3.org/Archives/Public/www-style/2008Feb/thread.html#msg35">Bert's syntax proposal</a>.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2007Dec/0119.html">Comment</a> from Simon Proctor 19 Dec 2007
<tr class=r><td>14<td>

Introducing a 'supports()' querying feature.

<td>Too late for this version. We should reconsider this for Media Queries Level 4.

<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Mar/0444.html">Comment</a> from Anne van Kesteren Mon, 31 Mar 2008.</a>

<tr class=a><td>15<td>I was wondering why a negative &lt;length> for 'width' (and other media features)
is not disallowed ... I hope a further revision of the specification could say that "&lt;length> must be
a positive integer when applied to a media feature specified in this
specification." (Perhaps adding "or zero" to that for clarity if needed.)

<td>
With my editor's hat on I went through all the features and clarified what type of "numbers" they could hold and whether those could be negative, zero, or just positive.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080406181816.GA25391@ridley.dbaron.org">Comment</a> from David Baron 06 Apr 2008
<tr class=a><td>16<td>

What does '(scan)' mean?

<td>The draft is clarified to mention that each media feature (including min/max prefixed)
"(media-feature)" is equivalent to "(media-feature:x)" for when x is not equal to 0. (If media-feature does not accept 0 x can be any value.)


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080407041829.GA18449@ridley.dbaron.org">Comment</a> from David Baron 07 Apr 2008
<tr class=a><td>17<td>

Bad examples for orientation. (Only value was given.)

<td>Examples are fixed.

<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080407040008.GA17448@ridley.dbaron.org">Comment</a> from David Baron 07 Apr 2008
<tr class=a><td>18<td>

Is 'resolution' in terms of CSS or device pixels?

<td>Should be device pixels.


<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Apr/0457.html">Comment</a> from fantasai 24 Apr 2008
<tr class=a><td>19<td>

Definitions of 'height' / 'width' / 'device-height' / 'device-width' need rewording.

<td>Reworded as suggested later in the thread.


<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Jun/0045.html">Comment</a> from Stewart Brodie 6 Jun 2008
<tr class=a><td>20<td>

Does the 'resolution' feature take a float or integer?

<td>Defined &lt;resolution> to take an &lt;float> immediately followed by a unit identifier per <a href="http://www.w3.org/mid/4856E023.9010003@inkedblade.net">this e-mail from fantasai</a>.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/484D9F48.80405@inkedblade.net">Comment</a> from fantasai 9 Jun 2008
<tr class=r><td>21<td>

Do we need special wording for display-level transformations, like zooming and N-up printing?

<td>We're not going into this level of detail for now.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080611215625.GA30548@pickering.dbaron.org">Comment</a> from David Baron 11 Jun 2008
<tr class=a><td>22<td>

Allow whitespace around '/' for the aspect-ratio and device-aspect-ratio media features.

<td>Agreed.

<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080618220428.GA10229@pickering.dbaron.org">Comment</a> from David Baron 19 Jun 2008
<tr class=a><td>23<td>
<pre>http://dev.w3.org/csswg/css3-mediaqueries/#media1 says:
  # For a media feature feature, (feature) will evaluate to true if
  # (feature:x) will evaluate to true for a value x other than zero.
 
Does this mean:
 
  (a) (width) is always true, even if the viewport width is zero,
  because "0px" is a value other than zero, or:
 
  (b) (width) is false when the viewport width is zero because "0px"
  and "0" are both not "other than zero"?
 
I'd also note that because specified widths cannot be negative,
(max-width) currently behaves the same as (width), whereas
(min-width) is always true.  Is that really intended?</pre>

<td>Zero is clarified to mean 0px, 0, etc. <a href="http://lists.w3.org/Archives/Public/www-style/2008Sep/0002.html">Min/max prefixed media features without values cannot be used</a>.

<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/20080619203334.GA30094@pickering.dbaron.org">Comment</a> from David Baron 19 Jun 2008
<tr class=a><td>24<td>
<pre>After reading http://dev.w3.org/csswg/css3-mediaqueries/#grid it's
not clear to me whether the queries "(grid: -1)" or "(grid: 2)"
should be parse errors or should always be false.  It should be
clear.</pre>

<td><a href="http://www.w3.org/mid/op.ughpofcf64w2qv@annevk-t60.oslo.opera.com">Clarified</a> they are indeed parse errors.


<tr><th colspan=3 class=source><a href="http://lists.w3.org/Archives/Public/www-style/2008Oct/0328.html">Comment</a> from Dean Jackson 30 Oct 2008
<tr class=r><td>25<td>The request is changing the syntax of aspect-ratio and
device-aspect-ratio to floats and orientation to angles.
<td>The WG decided to not make a change here. The WG also decided to keep aspect-ratio and device-aspect-ratio and not drop them as suggested in the follow-up thread.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/9fbcac550809220609g484b1ef3l7c4fbe9908b3d6dc@mail.gmail.com">Comment</a> from Jens Meiert 22 Sep 2008
<tr class=a><td>26<td>Editorial.
<td>Fixed.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/48FF5CA3.5070406@xwiki.com">Comment</a> from Sergiu Dumitriu 23 Oct 2008
<tr class=a><td>27<td>Editorial comments. Also a question whether 'ex' should be described for tty since 'em' is defined.
<td>The WG decided to remove the definition of 'em' for tty and leave that definition up to the values &amp; units draft.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/Pine.LNX.4.63.0902242324240.6949@master.abisoft.spb.ru">Comment</a> from Andrey Mikhalev 25 Feb 2009
<tr class=a><td>28<td>The grammar mixes CSS2 grammar and CSS core grammar productions.
<td>Fixed by using expr rather than value.


<tr><th colspan=3 class=source><a href="http://www.w3.org/mid/op.ulukkazr64w2qv@annevk-t60.oslo.opera.com">Comment</a> from Anne van Kesteren 8 Dec 2008
<tr class=a><td>29<td>Media queries has the implied suggestion to violate core grammar error handling.
<td>Added a note of a clarification per fantasai's suggestion.






<!--


	http://lists.w3.org/Archives/Public/www-style/2005Jul/0414.html
		6.2. height typo
		FIXED, outright error


	http://lists.w3.org/Archives/Public/www-style/2003Dec/0016
		NO, just a question




	http://lists.w3.org/Archives/Public/www-style/2002Jul/0089.html
	http://lists.w3.org/Archives/Public/www-style/2002Jul/0088.html
		NO

	http://lists.w3.org/Archives/Public/www-style/2002Jul/0075
		I found a few grammatical errors 
		EDITORIAL
	
	http://lists.w3.org/Archives/Public/www-style/2002Jul/0006
		Small errors I noticed:
		EDITORIAL

	http://lists.w3.org/Archives/Public/www-style/2002Mar/0073
		IRRELEVANT

	http://lists.w3.org/Archives/Public/www-style/2002Mar/0022
	http://lists.w3.org/Archives/Public/www-style/2002Feb/0151
		I attach my comments on the Last Call Working Draft of Media Queries 
		DISCUSS

	http://lists.w3.org/Archives/Public/www-style/2002Feb/0157
		WAI/PF comments
		EDITORIAL?

	http://lists.w3.org/Archives/Public/www-style/2002Feb/0145
		EDITORIAL

	http://lists.w3.org/Archives/Public/www-style/2002Feb/0117
		EDITORIAL

	http://lists.w3.org/Archives/Public/www-style/2002Feb/0048
		CREDIT, suggests dpcm, 

	http://lists.w3.org/Archives/Public/www-style/2001Apr/0025
		CREDIT, from RIJK, credit


	CSS-WG
	http://lists.w3.org/Archives/Member/w3c-css-wg/2006AprJun/0126.html
		media queries syntax
	http://lists.w3.org/Archives/Member/w3c-css-wg/2006AprJun/0153



-->
</table>
